Authentication and pairing of devices using a machine readable code

ABSTRACT

An MR code is generated within a browser on a client device and is read by a mobile application on a mobile device. A communication channel is then established through a web-based service, between the browser and the mobile application on the mobile device. The mobile application generates a user interface display on the mobile device that allows user selection of content. The mobile application sends a link to that content to the browser, which accesses and renders the content on the client device. User input commands to control the rendered content are also received at the mobile device and sent to the browser through the communication channel.

BACKGROUND

Some computer systems currently exist that allow a user to sign in, andpresent content on one computing device, while controlling it fromanother computing device. For instance, some systems allow a user tosign in and control a large screen device, using the user's mobiledevice.

Such systems usually have a user login to one or the other computingdevice. Many users do not feel comfortable using their username andpassword, especially on a computing device that they do not own. Userscan be concerned that key strokes are logged and the information will besurreptitiously used.

There also currently exist some systems for pairing computing devices sothat they can communicate with each other in a trusted way. One currentprocess for doing this has a user first pick a nearby device. It thenprompts the user to enter an identical code on both devices. Otherprocesses use the proximity of the two devices to automatically connect,and prompt the user on each device, ensuring that no unintendedconnections are made.

In other systems, if the user is logged in on all of his or her devices,then two devices can communicate in a trusted way. However, the usernormally needs to go through a prior setup process. Thus, the usernormally needs to own all of the devices being set up in this fashion.

Current systems also allow a user to present content on a large screendevice, using a mobile device. One current system for doing this has theuser connect the mobile device to the large screen device by plugging anHDMI, DVI, or other connection cable. This type of system streams theview of the content from the mobile device to the larger screen.However, the direct hard wiring can present certain problems. Othersystems have attempted to perform this type of communication wirelessly,but they involve the use of a pairing mechanism, which can be quite timeconsuming. In all of these types of systems, the amount of data thatneeds to be transmitted from the mobile device to the large screendevice is generally very high.

In the systems discussed above that pair two devices, the user normallyneeds to login on both of the paired devices. There then exists achannel for the devices to communicate with one another. This does notaddress a scenario in which a user may walk into a colleague's office,and wishes to share a document on the colleague's computer. Themechanism by which this is currently done is to have the user login tothe colleague's computer and then manually search for the content ordocument.

Machine readable labels (or MR codes) are labels that containinformation about an item. Some examples of MR codes include opticalcodes, such as barcodes, matrix barcodes (such as QR codes) and extendedmatrix barcodes, among others. Other examples of MR codes are codes thatare transmitted using near field communication.

The discussion above is merely provided for general backgroundinformation and is not intended to be used as an aid in determining thescope of the claimed subject matter.

SUMMARY

An MR code is generated within a browser on a client device and is readby a mobile application on a mobile device. A communication channel isthen established through a web-based service, between the browser andthe mobile application on the mobile device. The mobile applicationgenerates a user interface display on the mobile device that allows userselection of content. The mobile application sends a link to thatcontent to the browser, which accesses and renders the content on theclient device. User input commands to control the rendered content arealso received at the mobile device and sent to the browser through thecommunication channel.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The claimed subject matter is not limited to implementationsthat solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-1 and 1-2 (collectively FIG. 1) show a block diagram of oneembodiment of an authentication and pairing architecture.

FIG. 1A is a simplified flow diagram showing how a mobile device andanother client device establish a communication channel.

FIG. 2 is a flow diagram illustrating one embodiment of the operation ofthe architecture shown in FIG. 1 in which a user logs in to a mobileapplication.

FIGS. 3-1 and 3-2 (collectively FIG. 3) show a flow diagram illustratingone embodiment of the operation of the architecture shown in FIG. 1 inauthenticating a user and establishing a connection between a mobileapplication and a browser on a client device.

FIGS. 3A and 3B are illustrative user interface displays.

FIG. 4 is a flow diagram illustrating one embodiment of the operation ofthe architecture shown in FIG. 1 in allowing a user to display contenton the client device, under the control of the mobile device.

FIGS. 4A-4J are exemplary user interface displays.

FIG. 5 is a block diagram of one embodiment of the architecture shown inFIG. 1, deployed in a cloud computing architecture.

FIGS. 6-10 show various embodiments of mobile devices.

FIG. 11 is a block diagram of one illustrative computing environment.

DETAILED DESCRIPTION

FIGS. 1-1 and 1-2 (collectively FIG. 1) show a block diagram of oneillustrative authentication and pairing architecture 100. Architecture100 includes mobile device 102, another client device 104, a set ofweb-based services including an MR code management system 106, a sessionmanagement system 108 and a web-based remote control system 110. It alsoillustratively includes a set of content services 112. In the embodimentshown in FIG. 1, mobile device 102 illustratively includes processor114, user interface component 116, scanning component 118, and clientremote control system 120 (which can be a mobile application run onmobile device 102), and it can include other components 122 as well.

Architecture 100 will be described herein with respect to an example inwhich the MR code is an optical code, that is scanned by scanningcomponent 118. However, it can also be other MR codes, such as a codepresented using near field communication, or a code that is presentedaudibly and read and decoded using a listening component, such as amicrophone. All of these configurations are contemplated herein.

Remote control system 120, itself, includes authentication component124, link communication component 126, visualization component 128 andcommand communication component 130. Mobile device 102 illustrativelygenerates user interface displays 132, with user input mechanisms 134,for interaction by user 136. As is described in greater detail below,client device 104 can also generate such user interface displays anduser input mechanisms.

While a more detailed description of some exemplary mobile devices isprovided below with respect to FIGS. 6-10, the authentication andpairing processes described herein will refer to mobile device 102.

Client device 104 illustratively includes processor 138, user interfacecomponent 140, data store 142 and display device 144. It alsoillustratively includes browser 146 that, itself, includes renderingcomponent 148, command processing component 150, and other components152.

Content services 112 illustratively provide services that allow user 136to authenticate themselves using authentication component 154, andgenerate, and access, content 156. In one embodiment, the content 156 isauthored and accessed through a set of information worker applications,such as a word processing application, a spreadsheet application, apresentation application, or other applications. Therefore, the content156 can include word processing documents 158, spreadsheets 160,presentations 162, and other content 164.

FIG. 1 also shows that, in one embodiment, web-based remote controlsystem 110 includes a browser matching component 166. It can alsoinclude other components 168 as well.

Before describing the overall operation of architecture 100 in greaterdetail, a brief overview is first provided with respect to FIG. 1 andthe simplified flow diagram of FIG. 1A. User 136 can illustrativelyauthenticate himself or herself to architecture 100 and then havecontent rendered on client device 104 (which can be a desktop computer,large screen display device or other device), through browser 146, whilecontrolling that content with mobile device 102. To do this, in oneembodiment, user 136 first navigates to a login page of web-based remotecontrol system 110 using client device 104. Client device 104 receivesan MR code and displays it on display device 144. This is indicated byblock 170 in FIG. 1A. User 136 scans the MR code using scanningcomponent 118 of mobile device 102. This is indicated by block 172. Inresponse, browser matching component 166 of web-based remote controlsystem 110 establishes a connection between browser 146 and clientremote control system 120. This is indicated by block 174. Client remotecontrol system 120 can thus provide browser 146 with links to content156. Using authentication information provided by user 136, browser 146obtains the desired content 156 and renders it on display device 144.User 136 can then use client remote control system 120 to providecommands to browser 146 using the communication channel that has beenestablished through web-based remote control system 110, to navigatethrough, and otherwise control, the content being rendered by browser146 on display device 144. This is indicated by block 176 in FIG. 1A.

FIG. 2 is a more detailed flow diagram illustrating one embodiment ofthe operation of architecture 100, in allowing user 136 to initiallyauthenticate himself or herself with client remote control system 120and web-based remote control system 110. In one embodiment, since mobiledevice 102 is illustratively a personal device, user 136 only needs tosign in or authenticate himself or herself once. This can be performedduring the initial launch of client remote control system 120 orotherwise. Mobile device 102 thus initially receives user inputs fromuser 136 indicating that the user wishes to access the client remotecontrol system 120. This is indicated by block 180 in FIG. 2.

User interface component 116, either under the control of client remotecontrol system 120, or by itself, then generates a user interfacedisplay for authentication of user 136. It also receives authenticationinformation from the user. This is indicated by block 182. Theauthentication information can take a variety of different forms. In oneembodiment, it comprises a username and password 184. However, it caninclude other information 186 as well.

Authentication component 124 in client remote control system 120 thenverifies the credentials entered by user 136. This is indicated by block188 in FIG. 2. This can be done by providing the credentials to contentservices 112 or another service that verifies credentials for user 136.In response, component 124 receives an access token 190 corresponding touser 136. Authentication component 124 then illustratively stores theaccess token 190 for user 136, once the credentials have beenidentified.

FIGS. 3-1 and 3-2 (collectively FIG. 3) show a flow diagram illustratingone embodiment of the operation of architecture 100 in allowing user 136to establish a communication channel between client remote controlsystem 120 and browser 146 on client device 104, through web-basedremote control system 110. Browser 146 first receives user inputs onclient device 104 navigating to the web-based service 110 for connectionto client remote control system 120. This is indicated by block 200 inthe flow diagram of FIG. 3. Web-based remote control system 110 thenaccesses session management system 108, which manages various sessionswithin architecture 100. System 108 provides web-based remote controlsystem 110 with a unique session identifier (session ID). This isindicated by block 202. Web-based remote control system 110 alsoaccesses MR code management system 106 to obtain a MR code that encodesthe session ID obtained from system 106. This is indicated by block 204in FIG. 3.

If the user has not yet launched client remote control system 120 onmobile device 102, mobile device 102 receives user inputs launching theclient remote control system 120. This is indicated by block 206 in FIG.3. This can be done by the user providing sign in information 208, or inother ways 210.

At some point, web-based remote control system 110 displays the MR code,that encodes the session ID, within browser 146. The display isillustratively generated on display device 144 of client device 104.This is indicated by block 212 of FIG. 3. FIG. 3A shows one illustrativeuser interface display indicating this. Display 214 in FIG. 3A isillustratively displayed within browser 146, on display device 144. Itcan include a variety of display elements corresponding to underlyingapplications. It also illustratively includes a display of the MR code(which in the embodiment shown in FIG. 3A is embodied as a QR code) 216.

User 136 then maneuvers mobile device 102 into place with respect todisplay device 144 so that user 136 can actuate the scanning component118 of mobile device 102 in order to scan the QR code displayed ondisplay device 146. This is indicated by block 218 in the flow diagramof FIG. 3.

Mobile device 102 then decodes the QR code to obtain the session ID thatis encoded in the QR code. This is indicated by block 220 in FIG. 3.Mobile device 102 then sends the decoded session ID, along with theuser's authentication token, to the session management system 108. Thisis indicated by block 222 in FIG. 3.

Session management system 108 (which manages various sessions withinarchitecture 100) sends the session ID and the user's token for aspecific session ID to the web-based remote control system 110. This isindicated by block 224 in FIG. 3. In response, the web-based remotecontrol system authenticates the session ID. This is indicated by block226 in FIG. 3. In doing so, browser matching component 166illustratively matches browser 146 with the client remote control system120. This is indicated by block 228. It also illustratively sets up atrusted data transmission channel between browser 146 and client remotecontrol system 120 through web-based remote control system 110. This isindicated by block 230. The browser 146 and client remote control system120 on mobile device 102 both set up connections with web-based remotecontrol system 110. In one embodiment, they set up socket connections toobtain the trusted data transmission channel. This is indicated by block232 in FIG. 3.

Web-based remote control system 110 then passes the user's token tobrowser 146, so that browser 146 can use it to obtain access to theuser's content 156. This is indicated by block 234 in the flow diagramof FIG. 3. The authentication can be performed in other ways as well,and this is indicated by block 236.

During the processing of blocks 222-236 in FIG. 3, the user interfacecomponents 116 and 140 on mobile device 102 and client device 104 cangenerate displays indicating that the signup process is beingundertaken. FIG. 3B shows one example of this. User interface display238 is one exemplary display that can be generated on the display device144 of client device 104, and user interface display 240 is one exampleof a display that can be generated on the display device of mobiledevice 102.

Once the connection is established between browser 146 and client remotecontrol system 120, the user can use the matched browser to performremote control operations. This is indicated by block 242 in FIG. 3. Forinstance, link communication component 126 can send links, to content156, to rendering component 148 in browser 146. This allows browser 146to access the desired content. This is indicated by block 244 in FIG. 3.Rendering component 148 can then open the content on display device 144of client device 104. This is indicated by block 246 in FIG. 3. Commandcommunication component 130 can also send commands to command processingcomponent 150 in browser 146 (again using the data transmission channelset up through web-based remote control system 110). This is indicatedby block 248 in FIG. 3. Rendering component 148 can then performpresentation commands on presented content, based upon the commandsreceived from command communication component 130 on mobile device 102.This is indicated by block 250. The system can be used in other ways aswell, and this is indicated by block 252.

FIG. 4 is a flow diagram illustrating one embodiment of how user 136 canpresent content on the display device 144 of client device 104, usingmobile device 102. FIGS. 4A-4J are exemplary user interface displays.FIGS. 4-4J will now be described in conjunction with one another.

For purposes of FIG. 4, it is assumed that the communication channelbetween mobile device 102 (and specifically client remote control system120 on mobile device 102) and browser 146 is already established throughweb-based remote control system 110. This is indicated by block 260 inFIG. 4. Visualization component 128 on mobile device 102 then generatesa user interface display on mobile device 102 for user selection ofcontent. This is indicated by block 262 in FIG. 4.

FIG. 4A shows a set of user interface displays. User interface display264 is displayed by browser 146 on display device 144 of client device104. Display 266 is displayed by visualization component 128 on thedisplay device of mobile device 102. In the embodiment shown in FIG. 4A,display 266 shows a list 268 of most recently used items, displayed indate order. Each item in the list is illustratively a user actuatablelink that can be used to navigate to the corresponding content.

FIG. 4B is similar to FIG. 4A, and similar items are similarly numbered.However, FIG. 4B illustrates that a user is actuating a link 270corresponding to underlying content, which is a slide presentationentitled “2013 Overview”.

In response to user actuation of one of the links corresponding tounderlying content on mobile device 102, link communication component126 in client remote control system 120 sends the link (to the selectedcontent) to browser 146 using the trusted communication channelestablished through the web-based remote control system 110. This isindicated by block 272 in FIG. 4. Upon receiving the link, browser 146redirects to a specified page to access the selected content, using thelink and the user's token.

By way of example, assume that the slide presentation entitled “2013Overview”, that was actuated by the user in the description of FIG. 4,is located in presentations 162 in the content 156. Browser 146 uses theuser's token, and the link, to access the presentation from content 156.This is indicated by block 274 in the flow diagram of FIG. 4.

While this is happening, browser 146 and visualization component 128 cangenerate user interface displays on display device 144 and mobile device102, respectively, indicating this. FIG. 4C shows one set of exemplaryuser interface displays 264 and 266.

Once browser 146 accesses the content, rendering component 148 inbrowser 146 renders the content on display device 144 of client device104. Rendering the selected content in the browser on the device wherethe QR code was displayed is indicated by block 276 in FIG. 4. FIG. 4Dshows one set of exemplary user interfaces that indicate this.

The user interface display 264 on client device 104 shows that browser146 has opened the application where the presentation resides, and isdisplaying the first slide of the presentation. Visualization component128 on mobile device 102 generates display 266 that includes a userinput mechanism 278 that allows the user to enter presentation mode sothat the user can present the slide presentation on user interfacedisplay 264. Display 266 also includes an instruction for the user as tohow to return to the most recently used list of items to select anotheritem for display on user interface display 264. It can thus be seen thatuser interface display 264 on client device 104 is displaying theselected content, while user interface display 266 on mobile device 102displays a surface for entering commands to control the rendered contenton user interface display 264. Displaying the control surface on mobiledevice 102 is indicated by block 280 in the flow diagram of FIG. 4.

The surface displayed on mobile device 102 can include a wide variety ofdifferent user input mechanisms for performing a wide variety ofdifferent commands. For instance, the user input mechanisms can benavigation input mechanisms that allow the user to navigate within theselected content that is being displayed on user interface display 264of client device 104. This is indicated by block 282 in FIG. 4. It canalso include presentation command user input mechanisms so that the usercan easily provide presentation commands (such as back, forward, jump,enter presentation mode, etc.) for the selected content. This isindicated by block 284. Of course, the command surface can include awide variety of other commands as well, and this is indicated by block286.

Also, while the present discussion proceeds with respect to the examplein which commands and navigation inputs are provided through thedisplayed surface, they can be provided in other ways as well. Forinstance, they can be provided by an operator shaking device 102,tapping it, using it as a virtual laser pointer or providing otherinputs that can be sensed by an accelerometer or other sensors on device102.

As the user is controlling the content by entering commands on mobiledevice 102, visualization component 128 on mobile device 102 receivesthose inputs and command communication component 130 sends thosecommands to the command processing component 150 of browser 146 usingthe communication channel established through the web-based remotecontrol system 110. This is indicated by block 288. In response, browser146 reacts to those commands and renders the selected content in thedesired manner.

FIGS. 4E-4J show a number of different sets of user interface displaysthat illustrate this. FIG. 4E is similar to FIG. 4D except that it showsthat the user is actuating the user input mechanism 278 on the userinterface display 266 of mobile device 102. This indicates that the userwishes to enter presentation mode for the selected content shown in theuser interface display 264 of client device 104.

In response, command processing component 150 on browser 146 processesthis command and causes the selected content to be rendered inpresentation mode. FIG. 4F shows one illustrative set of user interfacedisplays that indicates this. FIG. 4F shows that the user interfacedisplay 264 on client device 104 has now entered the presentation mode,where the slide takes up substantially the entire display surface. FIG.4F also shows that visualization component 128 on mobile device 102 isnow displaying a control surface that allows the user to sendpresentation commands to browser 146 to control presentation of theselected content on user interface display 264. For instance, userinterface display 166 on mobile device 102 includes command buttons thatallow the user to move forward or backward or to jump through thevarious slides in the selected content being displayed on client device104.

FIG. 4G shows another exemplary set of user interface displays that canbe generated when the user has selected a word processing document,instead of a slide presentation. FIG. 4G is similar to FIG. 4D exceptthat the user interface display 264 generated by browser 146 on clientdevice 104 has now opened a word processing document. Similarly, theuser interface display 166 on mobile device 102 has the user inputmechanism 278, but instead of indicating that it will enter thepresentation mode for a slide presentation, it now indicates that, if itis actuated, it will enter presentation mode for a word processingdocument.

FIG. 4H is similar to FIG. 4G, except that it shows that the user is nowactuating user input mechanism 278, indicating that the user wishes topresent the word processing document that is opened within browser 146.In response, command communication component 130 on mobile device 102sends this command to the command processing component 150 in browser146, over the secured communication channel established throughweb-based remote control system 110. Browser 146 thus enterspresentation mode for the word processing document.

FIG. 4I shows one illustrative set of user interface displays indicatingthis. It can be seen in FIG. 4I that rendering component 148 in browser146 has now rendered the word processing document in presentation mode.It can also be seen in FIG. 4I that the visualization component 128 onmobile device 102 has now rendered a command surface on user interfacedisplay 266 of mobile device 102, so that the user can providenavigation commands to navigate through the word processing documentdisplayed in browser 146 on client device 104.

FIG. 4J shows yet another set of user interface displays. They indicatethat the user has selected a spreadsheet document. It can thus be seenthat browser 146 has accessed the spreadsheet document and opened it onthe user interface display 264 of client device 104. Similarly,visualization component 128 on mobile device 102 has generated a controlsurface 266 that allows the user to either enter into a control mode forcontrolling navigation on the spreadsheet (by actuating user inputmechanism 278) or to return to the most recently used list (or anothersurface) to select another item of content.

It can thus be seen that the architecture provides the ability to use adevice that is already signed in (such as a mobile phone application) asa source of identity to use when logging into another device. It alsoprovides the ability to pair a phone and another screen on anothercomputing device so that they can communicate in a trusted way. Thisreduces the number of steps that normal code matching requires and italso reduces the amount of input needed for systems that have a userenter a personal identification number. One of the devices simplydisplays an MR code, the other device scans it, and a third-partycreates a communication channel between the two. It also illustrativelyprovides the ability to send a link to selected content to a listeningservice (such as a browser window) that downloads and startspresentation of the selected content, rendering it remotely. Thepresentation can then be controlled by the mobile device, by sendingonly relatively simple commands to the rendering computing device. Italso provides the ability to select a document on a mobile device andhave it open on a paired screen. Rather than uploading the documentdirectly from the mobile device to the device that uses the pairedscreen, it simply passes a link to the selected content, and the pairedscreen device then accesses it using that link.

The present discussion has mentioned processors and servers. In oneembodiment, the processors and servers include computer processors withassociated memory and timing circuitry, not separately shown. They arefunctional parts of the systems or devices to which they belong and areactivated by, and facilitate the functionality of the other componentsor items in those systems.

Also, a number of user interface displays have been discussed. They cantake a wide variety of different forms and can have a wide variety ofdifferent user actuatable input mechanisms disposed thereon. Forinstance, the user actuatable input mechanisms can be text boxes, checkboxes, icons, links, drop-down menus, search boxes, etc. They can alsobe actuated in a wide variety of different ways. For instance, they canbe actuated using a point and click device (such as a track ball ormouse). They can be actuated using hardware buttons, switches, ajoystick or keyboard, thumb switches or thumb pads, etc. They can alsobe actuated using a virtual keyboard or other virtual actuators. Inaddition, where the screen on which they are displayed is a touchsensitive screen, they can be actuated using touch gestures. Also, wherethe device that displays them has speech recognition components, theycan be actuated using speech commands.

A number of data stores have also been discussed. It will be noted theycan each be broken into multiple data stores. All can be local to thesystems accessing them, all can be remote, or some can be local whileothers are remote. All of these configurations are contemplated herein.

Also, the figures show a number of blocks with functionality ascribed toeach block. It will be noted that fewer blocks can be used so thefunctionality is performed by fewer components. Also, more blocks can beused with the functionality distributed among more components.

FIG. 5 is a block diagram of architecture 100, shown in FIG. 1, exceptthat its elements are disposed in a cloud computing architecture 500.Cloud computing provides computation, software, data access, and storageservices that do not require end-user knowledge of the physical locationor configuration of the system that delivers the services. In variousembodiments, cloud computing delivers the services over a wide areanetwork, such as the internet, using appropriate protocols. Forinstance, cloud computing providers deliver applications over a widearea network and they can be accessed through a web browser or any othercomputing component. Software or components of architecture 100 as wellas the corresponding data, can be stored on servers at a remotelocation. The computing resources in a cloud computing environment canbe consolidated at a remote data center location or they can bedispersed. Cloud computing infrastructures can deliver services throughshared data centers, even though they appear as a single point of accessfor the user. Thus, the components and functions described herein can beprovided from a service provider at a remote location using a cloudcomputing architecture. Alternatively, they can be provided from aconventional server, or they can be installed on client devicesdirectly, or in other ways.

The description is intended to include both public cloud computing andprivate cloud computing. Cloud computing (both public and private)provides substantially seamless pooling of resources, as well as areduced need to manage and configure underlying hardware infrastructure.

A public cloud is managed by a vendor and typically supports multipleconsumers using the same infrastructure. Also, a public cloud, asopposed to a private cloud, can free up the end users from managing thehardware. A private cloud may be managed by the organization itself andthe infrastructure is typically not shared with other organizations. Theorganization still maintains the hardware to some extent, such asinstallations and repairs, etc.

In the embodiment shown in FIG. 5, some items are similar to those shownin FIG. 1 and they are similarly numbered. FIG. 5 specifically showsthat systems 106, 108 and 110 can be located in cloud 502 (which can bepublic, private, or a combination where portions are public while othersare private). Therefore, user 136 uses client device 104 to access thosesystems through cloud 502.

FIG. 5 also depicts another embodiment of a cloud architecture. FIG. 4shows that it is also contemplated that some elements of architecture100 can be disposed in cloud 502 while others are not. By way ofexample, content 156 can be disposed outside of cloud 502, and accessedthrough cloud 502. In another embodiment, system 110 can also be outsideof cloud 502. Regardless of where they are located, they can be accesseddirectly by device 104, through a network (either a wide area network ora local area network), they can be hosted at a remote site by a service,or they can be provided as a service through a cloud or accessed by aconnection service that resides in the cloud. All of these architecturesare contemplated herein.

It will also be noted that architecture 100, or portions of it, can bedisposed on a wide variety of different devices. Some of those devicesinclude servers, desktop computers, laptop computers, tablet computers,or other mobile devices, such as palm top computers, cell phones, smartphones, multimedia players, personal digital assistants, etc.

FIG. 6 is a simplified block diagram of one illustrative embodiment of ahandheld or mobile computing device that can be used as a user's orclient's hand held device 16, in which the present system (or parts ofit) can be deployed. FIGS. 7-10 are examples of handheld or mobiledevices.

FIG. 6 provides a general block diagram of the components of a clientdevice 16 (which can comprise client device 104 or mobile device 102 inpreceding Figures) that can run components of or that interacts witharchitecture 100, or both. In the device 16, a communications link 13 isprovided that allows the handheld device to communicate with othercomputing devices and under some embodiments provides a channel forreceiving information automatically, such as by scanning. Examples ofcommunications link 13 include an infrared port, a serial/USB port, acable network port such as an Ethernet port, and a wireless network portallowing communication though one or more communication protocolsincluding General Packet Radio Service (GPRS), LTE, HSPA, HSPA+ andother 3G and 4G radio protocols, 1×rtt, and Short Message Service, whichare wireless services used to provide cellular access to a network, aswell as 802.11 and 802.11b (Wi-Fi) protocols, and Bluetooth protocol,which provide local wireless connections to networks.

Under other embodiments, applications or systems are received on aremovable Secure Digital (SD) card that is connected to a SD cardinterface 15. SD card interface 15 and communication links 13communicate with a processor 17 (which can also embody processors 124,186 or 190 from FIG. 1) along a bus 19 that is also connected to memory21 and input/output (I/O) components 23, as well as clock 25 andlocation system 27.

I/O components 23, in one embodiment, are provided to facilitate inputand output operations. I/O components 23 for various embodiments of thedevice 16 can include input components such as buttons, touch sensors,multi-touch sensors, optical or video sensors, voice sensors, touchscreens, proximity sensors, microphones, tilt sensors, and gravityswitches and output components such as a display device, a speaker, andor a printer port. Other I/O components 23 can be used as well.

Clock 25 illustratively comprises a real time clock component thatoutputs a time and date. It can also, illustratively, provide timingfunctions for processor 17.

Location system 27 illustratively includes a component that outputs acurrent geographical location of device 16. This can include, forinstance, a global positioning system (GPS) receiver, a LORAN system, adead reckoning system, a cellular triangulation system, or otherpositioning system. It can also include, for example, mapping softwareor navigation software that generates desired maps, navigation routesand other geographic functions.

Memory 21 stores operating system 29, network settings 31, applications33, application configuration settings 35, data store 37, communicationdrivers 39, and communication configuration settings 41. Memory 21 caninclude all types of tangible volatile and non-volatilecomputer-readable memory devices. It can also include computer storagemedia (described below). Memory 21 stores computer readable instructionsthat, when executed by processor 17, cause the processor to performcomputer-implemented steps or functions according to the instructions.Processor 17 can be activated by other components to facilitate theirfunctionality as well.

Examples of the network settings 31 include things such as proxyinformation, Internet connection information, and mappings. Applicationconfiguration settings 35 include settings that tailor the applicationfor a specific enterprise or user. Communication configuration settings41 provide parameters for communicating with other computers and includeitems such as GPRS parameters, SMS parameters, connection user names andpasswords.

Applications 33 can be applications that have previously been stored onthe device 16 or applications that are installed during use, althoughthese can be part of operating system 29, or hosted external to device16, as well.

FIG. 7 shows one embodiment in which device 16 is a tablet computer 600.Computer 600 can comprise either client device 104 or mobile device 102from previous Figures. In FIG. 7, computer 600 is shown with userinterface display on the display screen 602. Screen 602 can be a touchscreen (so touch gestures from a user's finger can be used to interactwith the application) or a pen-enabled interface that receives inputsfrom a pen or stylus. It can also use an on-screen virtual keyboard. Ofcourse, it might also be attached to a keyboard or other user inputdevice through a suitable attachment mechanism, such as a wireless linkor USB port, for instance. Computer 600 can also illustratively receivevoice inputs as well.

FIGS. 8 and 9 provide additional examples of devices 16 that can beused, although others can be used as well. In FIG. 8, a feature phone,smart phone or mobile phone 45 is provided as the device 16. Phone 45includes a set of keypads 47 for dialing phone numbers, a display 49capable of displaying images including application images, icons, webpages, photographs, and video, and control buttons 51 for selectingitems shown on the display. The phone includes an antenna 53 forreceiving cellular phone signals such as General Packet Radio Service(GPRS) and 1×rtt, and Short Message Service (SMS) signals. In someembodiments, phone 45 also includes a Secure Digital (SD) card slot 55that accepts a SD card 57.

The mobile device of FIG. 9 is a personal digital assistant (PDA) 59 ora multimedia player or a tablet computing device, etc. (hereinafterreferred to as PDA 59). PDA 59 includes an inductive screen 61 thatsenses the position of a stylus 63 (or other pointers, such as a user'sfinger) when the stylus is positioned over the screen. This allows theuser to select, highlight, and move items on the screen as well as drawand write. PDA 59 also includes a number of user input keys or buttons(such as button 65) which allow the user to scroll through menu optionsor other display options which are displayed on display 61, and allowthe user to change applications or select user input functions, withoutcontacting display 61. Although not shown, PDA 59 can include aninternal antenna and an infrared transmitter/receiver that allow forwireless communication with other computers as well as connection portsthat allow for hardware connections to other computing devices. Suchhardware connections are typically made through a cradle that connectsto the other computer through a serial or USB port. As such, theseconnections are non-network connections. In one embodiment, mobiledevice 59 also includes a SD card slot 67 that accepts a SD card 69.

FIG. 10 is similar to FIG. 8 except that the phone is a smart phone 71.Smart phone 71 has a touch sensitive display 73 that displays icons ortiles or other user input mechanisms 75. Mechanisms 75 can be used by auser to run applications, make calls, perform data transfer operations,etc. In general, smart phone 71 is built on a mobile operating systemand offers more advanced computing capability and connectivity than afeature phone.

Note that other forms of the devices 16 are possible.

FIG. 11 is one embodiment of a computing environment in whicharchitecture 100, or parts of it, (for example) can be deployed. Withreference to FIG. 11, an exemplary system for implementing someembodiments includes a general-purpose computing device in the form of acomputer 810. Components of computer 810 may include, but are notlimited to, a processing unit 820 (which can comprise processor 114 or138), a system memory 830, and a system bus 821 that couples varioussystem components including the system memory to the processing unit820. The system bus 821 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. By way ofexample, and not limitation, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA)local bus, and Peripheral Component Interconnect (PCI) bus also known asMezzanine bus. Memory and programs described with respect to FIG. 1 canbe deployed in corresponding portions of FIG. 11.

Computer 810 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 810 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media is different from, anddoes not include, a modulated data signal or carrier wave. It includeshardware storage media including both volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by computer 810. Communication media typically embodiescomputer readable instructions, data structures, program modules orother data in a transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 830 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 831and random access memory (RAM) 832. A basic input/output system 833(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 810, such as during start-up, istypically stored in ROM 831. RAM 832 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 820. By way of example, and notlimitation, FIG. 11 illustrates operating system 834, applicationprograms 835, other program modules 836, and program data 837.

The computer 810 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 11 illustrates a hard disk drive 841 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 851that reads from or writes to a removable, nonvolatile magnetic disk 852,and an optical disk drive 855 that reads from or writes to a removable,nonvolatile optical disk 856 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 841 is typically connectedto the system bus 821 through a non-removable memory interface such asinterface 840, and magnetic disk drive 851 and optical disk drive 855are typically connected to the system bus 821 by a removable memoryinterface, such as interface 850.

Alternatively, or in addition, the functionality described herein can beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), etc.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 11, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 810. In FIG. 11, for example, hard disk drive 841 isillustrated as storing operating system 844, application programs 845,other program modules 846, and program data 847. Note that thesecomponents can either be the same as or different from operating system834, application programs 835, other program modules 836, and programdata 837. Operating system 844, application programs 845, other programmodules 846, and program data 847 are given different numbers here toillustrate that, at a minimum, they are different copies.

A user may enter commands and information into the computer 810 throughinput devices such as a keyboard 862, a microphone 863, and a pointingdevice 861, such as a mouse, trackball or touch pad. Other input devices(not shown) may include a joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 820 through a user input interface 860 that is coupledto the system bus, but may be connected by other interface and busstructures, such as a parallel port, game port or a universal serial bus(USB). A visual display 891 or other type of display device is alsoconnected to the system bus 821 via an interface, such as a videointerface 890. In addition to the monitor, computers may also includeother peripheral output devices such as speakers 897 and printer 896,which may be connected through an output peripheral interface 895.

The computer 810 is operated in a networked environment using logicalconnections to one or more remote computers, such as a remote computer880. The remote computer 880 may be a personal computer, a hand-helddevice, a server, a router, a network PC, a peer device or other commonnetwork node, and typically includes many or all of the elementsdescribed above relative to the computer 810. The logical connectionsdepicted in FIG. 11 include a local area network (LAN) 871 and a widearea network (WAN) 873, but may also include other networks. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 810 is connectedto the LAN 871 through a network interface or adapter 870. When used ina WAN networking environment, the computer 810 typically includes amodem 872 or other means for establishing communications over the WAN873, such as the Internet. The modem 872, which may be internal orexternal, may be connected to the system bus 821 via the user inputinterface 860, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 810, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 11 illustrates remoteapplication programs 885 as residing on remote computer 880. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

It should also be noted that the different embodiments described hereincan be combined in different ways. That is, parts of one or moreembodiments can be combined with parts of one or more other embodiments.All of this is contemplated herein.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A computer-implemented method, comprising:receiving, at a mobile device, a machine readable code (MR code) from aclient device; obtaining, at the mobile device, a session identifier(session id) from the MR code; sending the session id to a remotesystem; and in response to sending the session id to the remote system,receiving a pairing input at the mobile device that pairs the mobiledevice for communication with the client device over a communicationchannel through the remote system.
 2. The computer-implemented method ofclaim 1 wherein sending the session id to the remote system comprises:sending a user token authenticating a user, and the session id, to theremote system.
 3. The computer-implemented method of claim 1 whereinreceiving a pairing input comprises: receiving the pairing input tomatch the mobile device with a browser that has the user token foraccessing content accessible to the user.
 4. The computer-implementedmethod of claim 3 and further comprising: sending control outputs fromthe mobile device, based on control user inputs received at the mobiledevice, over the communication channel through the remote system tocontrol the screen on the client device.
 5. The computer-implementedmethod of claim 4 wherein sending control outputs comprises: sendingcontent control outputs controlling content rendering on the browser. 6.The computer-implemented method of claim 4 wherein sending contentcontrol outputs comprises: receiving user selection of a contentidentifier, on the mobile device, indicative of an item of contentaccessible to the user; and sending a link to the item of content to thebrowser over the communication channel.
 7. The computer-implementedmethod of claim 6 wherein the browser obtains access to the item ofcontent using the user token and renders the item of content on a screenof the client device, and wherein sending content control outputscomprises: receiving navigation command user inputs on the mobiledevice; and sending navigation commands, indicative of the navigationcommand user inputs, to the browser over the communication channel tocontrol navigation through the item of content on the screen of theclient device.
 8. The computer-implemented method of claim 6 wherein thebrowser obtains access to the item of content using the user token andrenders the item of content on a screen of the client device, andwherein sending content control outputs comprises: receivingpresentation command user inputs on the mobile device; and sendingpresentation commands, indicative of the presentation command userinputs, to the browser over the communication channel to controlpresentation of the item of content on the screen of the client device.